…tgresql

Weasel 9.0.0-alpha.5 ships in lockstep (Weasel.Postgresql ⇒ this PR's
existing bump, Weasel.EntityFrameworkCore ⇒ this commit). Picks up the
CREATE SCHEMA race fix from JasperFx/weasel#282 needed by the un-skipped
full_text_index tests on this branch.

…ma (#4446)

* [#4445] Un-skip full_text_index race-flake tests; isolate shared schema

Pairs with weasel#282, which catches the duplicate_schema / unique_violation
that two concurrent sessions race on when both emit "CREATE SCHEMA <name>".
With that DDL fix in Weasel.Postgresql 9.0.0-alpha.5, the FTI fixture passes
deterministically as a suite (was 3+ tests failing intermittently with
"23505 pg_namespace_nspname_index").

The "fulltext"-schema test additionally has a data-accumulation problem
independent of the race: DocumentStore.For() with a custom DatabaseSchemaName
bypasses OneOffConfigurationsContext's cleanAll step (which only drops the
fixture's own schema). Drop the "fulltext" schema in a pre-flight outside the
#region so the docs sample stays clean.

* Bump Weasel.EntityFrameworkCore to 9.0.0-alpha.5 alongside Weasel.Postgresql

Weasel 9.0.0-alpha.5 ships in lockstep (Weasel.Postgresql ⇒ this PR's
existing bump, Weasel.EntityFrameworkCore ⇒ this commit). Picks up the
CREATE SCHEMA race fix from JasperFx/weasel#282 needed by the un-skipped
full_text_index tests on this branch.

closes #293) (#294)

Follow-up to #282. That fix wrapped only CREATE SCHEMA in a plpgsql block
catching 42P06/23505. The rest of the migration DDL emitted by
migration.WriteAllUpdates(...) — CREATE OR REPLACE FUNCTION mt_immutable_*,
CREATE TABLE IF NOT EXISTS, etc. — stayed unguarded, so concurrent lazy
EnsureStorageExists against the same database could fail with
"XX000: tuple concurrently updated" (two backends updating the same
pg_proc / catalog row at once). Seen as a Marten conjoined multi-tenant CI
flake (JasperFx/marten#4552).

The DDL Weasel emits is idempotent (IF NOT EXISTS / CREATE OR REPLACE) and
executeDelta runs each statement on the bare connection (autocommit, no
ambient transaction), so a statement that lost a catalog race is safe to
re-run from a clean slate. Wrap each cmd.ExecuteNonQueryAsync in a bounded
retry (3 attempts, jittered sub-100ms backoff) keyed on the transient
SQLSTATEs:

  - 40001 serialization_failure
  - 40P01 deadlock_detected
  - XX000 internal_error ONLY when the message is "tuple concurrently
    updated" (XX000 is a catch-all, so the message guard avoids
    blanket-retrying unrelated internal errors)

The retry sits inside the existing try/catch, so after exhausting attempts
the established logger.OnFailure / rethrow path is unchanged. Kept
PG-specific (these SQLSTATEs are PostgreSQL's; executeDelta is a per-provider
override).

The classification is extracted as a pure internal predicate
IsTransientCatalogConcurrency(sqlState, messageText) and covered by 12 unit
assertions (the race itself isn't deterministically testable). Happy-path
migration/schema integration tests pass unchanged (21/22, 1 pre-existing
skip). Downstream Marten#4552 stabilizes once it consumes a Weasel build
with this.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>